feat: API Gateway emulator HTTP proxy so non-Lambda backends share the emulator origin - #2569
Merged
normj merged 3 commits intoSep 17, 2026
Conversation
…ends Add optional IntegrationType=Http so emulator routes can reverse-proxy to an HTTP Endpoint instead of invoking Lambda, keeping a single emulator origin for mixed local topologies. Closes aws#2568 Co-authored-by: Cursor <cursoragent@cursor.com>
normj
approved these changes
Sep 16, 2026
normj
left a comment
normj
left a comment
Member
There was a problem hiding this comment.
Cool feature! Thanks for the contribution. I pushed a commit to your branch updating the README.md.
boblodgett
reviewed
Sep 17, 2026
| /// <summary> | ||
| /// The integration type: "Lambda" (default) or "Http". When "Http", the request is proxied to the Endpoint URL instead of invoking a Lambda. | ||
| /// </summary> | ||
| public string? IntegrationType { get; set; } |
Contributor
There was a problem hiding this comment.
Is there a reason to not use an enum so the values are automatically known outside of the comment? Easier to match values / not make coding mistakes in the future.
Contributor
Author
There was a problem hiding this comment.
You're right, I just changed it
Address review feedback on PR aws#2569: replace string IntegrationType with an enum (Lambda | Http), serialized as strings via JsonStringEnumConverter so existing route-config JSON and Aspire env vars keep working. Co-authored-by: Cursor <cursoragent@cursor.com>
Contributor
Author
|
Addressed @boblodgett's feedback: \IntegrationType\ is now \ApiGatewayIntegrationType\ (\Lambda\ | \Http), with \JsonStringEnumConverter\ so route-config JSON still uses "Http" / "Lambda" strings. |
boblodgett
approved these changes
Sep 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Closes #2568
Description of changes:
Adds an optional HTTP proxy integration to the Lambda Test Tool v2 API Gateway emulator so non-Lambda HTTP backends can share the same emulator origin as Lambda routes.
Behavior
ApiGatewayRouteConfig.IntegrationType:Lambda/ omitted (default) — existing event translation → Runtime APIHttp— reverse-proxy the incoming HTTP request toEndpoint(no API Gateway JSON event wrapping)Httproutes have a non-empty absolutehttp(s)EndpointIHttpClientFactoryfor the proxy pathWhy
API Gateway supports HTTP integrations, not only Lambda. Local mixed topologies (Kestrel / containers / App Runner behind the same gateway URL the frontend already uses) need the emulator to represent that.
Tests
Unit tests for accepting valid
Httpconfigs and rejecting missing/invalid endpoints.Out of scope
RequestContext/ AspNetCoreServer null-safety — API Gateway emulator builds incomplete APIGatewayProxyRequest; AspNetCoreServer NREs on null Path / RequestContext / headers #2566 / fix: complete emulator REST APIGatewayProxyRequest and null-safe AspNetCoreServer marshalling #2567By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.